State Restauration does not work anymore for me. I see encodeRestorableStateWithCode is called and something written to disk but it's not reloaded at all. And this is what hte warning is all about, so it is not line noise. And also in my case i have an extra space in front of the file name in the URL. Running MacOS 14.5 and XCode 16.2 and i am getting very frustated about all the RestoreState problems.

+[NSStream getStreamsToHostWithName:port:inputStream:outputStream:]. is now deprecated, what should we do now? This permanent never ending deprecation without reasoning and giving the new recommendation in the documention is driving me crazy

It might happen, but definitely not for your reasons because they still have to support C++ and C as this are the low level languages. And i can't see any reason why they would remove it from XCode. It's a failure Microsoft regrets to bet everything on C# and now they come back to C++ with WinRT. You might not be informed enough to understand that the Darwin core and even the new TextKit2 (published just in 2021) is written in this languages. You can't replace an architecture without removing but you don't need to replace a language with the same binary object model. Also the business logic behind the Catalina 32-bit end was just to get the bad marketing out of the Arm switch. Everyone blames Catalina now for breaking incompatibility. A smart move from Apple. Swift is only the user interface language. But yeah, Objective-C is also only a user interface language. The main reason to still use Objective-C is the for free integration with a C++ business layer.